Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Core][Worker_Pool] Wait for prestarted-workers for the first job and disable run_on_all_workers flaky tests #31836

Merged
merged 7 commits into from
Jan 22, 2023

Conversation

scv119
Copy link
Contributor

@scv119 scv119 commented Jan 21, 2023

Why are these changes needed?

#30883 we changed the behavior of first driver connect to a raylet: previously the driver connection will wait for the prestarted workers to connect before returns, and after #30883 it no longer does so. This has caused some test flakiness for
test_failure_4.py -k test_task_crash_after_raylet_dead_throws_node_died_error and test_ray_shutdown.py -k test_driver_dead

We restore the previous behavior and fixes the test flakiness.

Also #30883 added flakiness for run_functions_on_all_workers. we disable those flaky tests

Related issue number

Checks

  • I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
  • I've run scripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed for https://docs.ray.io/en/master/.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

@scv119 scv119 marked this pull request as ready for review January 21, 2023 18:41
Copy link
Contributor

@rickyyx rickyyx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Stamped.

@scv119 scv119 added the @author-action-required The PR author is responsible for the next step. Remove tag to send back to the reviewer. label Jan 21, 2023
Comment on lines 765 to 767
// This is a workaround to finish driver registration after all initial workers are
// registered to Raylet if and only if Raylet is started by a Python driver and the
// job config is not set in `ray.init(...)`.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Under what circumstances would the raylet be started by a Python driver?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think only local mode (starting ray with ray.init...)

src/ray/raylet/worker_pool.cc Outdated Show resolved Hide resolved
@scv119 scv119 changed the title [Core][Worker_Pool] Wait for prestarted-workers for the first job [Core][Worker_Pool] Wait for prestarted-workers for the first job and disable run_on_all_workers flaky tests Jan 21, 2023
@scv119 scv119 merged commit 76364c7 into ray-project:master Jan 22, 2023
andreapiso pushed a commit to andreapiso/ray that referenced this pull request Jan 22, 2023
… disable run_on_all_workers flaky tests (ray-project#31836)

Why are these changes needed?

ray-project#30883 we changed the behavior of first driver connect to a raylet: previously the driver connection will wait for the prestarted workers to connect before returns, and after ray-project#30883 it no longer does so. This has caused some test flakiness for
test_failure_4.py -k test_task_crash_after_raylet_dead_throws_node_died_error and test_ray_shutdown.py -k test_driver_dead

We restore the previous behavior and fixes the test flakiness.

Also ray-project#30883 added flakiness for run_functions_on_all_workers. we disable those flaky tests

Signed-off-by: Andrea Pisoni <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@author-action-required The PR author is responsible for the next step. Remove tag to send back to the reviewer.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants